<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2776/Taking-Quality-for-Granted.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2776</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2776&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Taking Quality for Granted</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2776/Taking-Quality-for-Granted.aspx</link> 
    <description>&amp;nbsp;Quality must be built into the product during design, not inspected in afterwards.&amp;nbsp;Beyond the mechanics of quality though, people must learn to care about the work products they are charged to produce. &amp;nbsp;Quality requires both discipline and a conscientious work force. You cannot have one without the other.
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Sun, 14 Jan 2024 08:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2776</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5123/How-Effective-Were-You-Today.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5123</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5123&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How &quot;Effective&quot; Were You Today?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5123/How-Effective-Were-You-Today.aspx</link> 
    <description>Okay, you believe you had a great day at work today; that you accomplished a lot. Maybe you did. Then again, maybe you didn&amp;#39;t do as much as you might think. A lot of people believe just because they are a model of efficiency, they are being highly productive. This is simply not true. We have discussed the concept of productivity on more than one occasion in this column, but some trends in the business world have caused me to revisit it again.
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Sun, 24 Dec 2023 11:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5123</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4926/Managing-Consultants.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=4926</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=4926&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Managing Consultants</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4926/Managing-Consultants.aspx</link> 
    <description>My single most important recommendation to anyone considering the use of outside consultants is simple: Get everything in writing! Clearly define the work assignment, get a signed agreement spelling out the terms of the assignment, and demand regular status reports.

I am always amazed how companies give consulting firms carte blanche to perform project work as they see fit. Abdicating total control to a consultant is not only irresponsible, it is highly suspicious and may represent collusion and kickbacks.

There is nothing magical in managing consultants. It requires nothing more than simple planning, organization, and control. If you are not willing to do this, then do not be surprised with the results produced. Failure to manage a consultant properly or to adequately inspect work in progress will produce inadequate results. So, do yourself (and your company) a favor, do your homework and create a win-win scenario for both the consultant and yourself.
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Sun, 17 Sep 2023 18:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:4926</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1579/Why-We-No-Longer-Think-BIG.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1579</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1579&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Why We No Longer Think &#39;BIG&#39; </title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1579/Why-We-No-Longer-Think-BIG.aspx</link> 
    <description>&amp;nbsp;
The design of major systems need not be a complicated process couched in a cryptic vocabulary using seemingly esoteric techniques. While the state of the art in programming has undergone considerable changes over the last half century, little progress has been made in the area of systems which has stagnated due to the lack of standards and the heavy emphasis on programming.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Mon, 04 Feb 2019 01:02:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1579</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5242/Heigh-Ho-Heigh-Ho-Its-Back-to-Work-We-Go.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5242</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5242&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Heigh Ho, Heigh Ho, It&#39;s Back to Work We Go</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5242/Heigh-Ho-Heigh-Ho-Its-Back-to-Work-We-Go.aspx</link> 
    <description>Nonetheless, it&#39;s a new year, and time to go back to work. January is when we reset the statistics, brace for a new year, and try to prove ourselves once again. Some people have trouble getting back into the swing of work after the holidays; they&#39;ve probably slept too much, partied too much, and ate way too much, which explains the five-to-eight pounds they&#39;ve put on. This is why dieting and temperance are among the top New Year&#39;s resolutions. Regardless, they are having trouble focusing on their work.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 10 Jan 2019 12:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5242</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4918/Craftsmanship-The-Meaning-of-Life.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=4918</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=4918&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Craftsmanship:  The Meaning of Life</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4918/Craftsmanship-The-Meaning-of-Life.aspx</link> 
    <description>Quality and service used to be considered paramount in this country. If it wasn&#39;t just right, you were expected to do it over again until you got it right. We cared about what we produced because it was a reflection of our personal character and integrity. But somewhere along the line we lost our way and craftsmanship has fallen by the wayside. Why? Probably because we no longer care.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 31 May 2018 12:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:4918</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4916/Individualism-vs-Teamwork.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=4916</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=4916&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Individualism vs. Teamwork</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4916/Individualism-vs-Teamwork.aspx</link> 
    <description>Are we really trying to promote teamwork or is this nothing more than the latest corporate fad that is being implemented more for public relations than anything else? Let&#39;s hope for the former and not the latter. Teamwork is a powerful concept, particularly when there is anything of substance to be done.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Sun, 07 Jan 2018 13:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:4916</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3235/BOM-Project-Estimating.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3235</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3235&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>BOM Project Estimating</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3235/BOM-Project-Estimating.aspx</link> 
    <description>Estimating is one of the most controversial subjects in project management. There are some people who have turned the subject into a cryptic science involving esoteric techniques.
Estimating is simply the process used to determine the amount of effort and cost required to implement a project, in part or in full. It is important to acknowledge that estimating is fundamentally an effort at projecting the future. Like all projections, the more facts and information available, the better the estimate. There is a natural human tendency to avoid making estimates because estimates represent commitments, and people tend to shy away from commitments, particularly when they are not sure of the facts. Nevertheless, little progress would be made if we never attempted to plan for the future.
Most estimating errors are errors of omission, not commission. It is what we forget to estimate that often leads to problems. Methodologies, with their defined structure, materially assists with eliminating some of the unknowns when estimating. They provide frameworks and structures acting as checklists for estimating. Methodologies isolate the activities to be performed into small enough increments, thereby minimizing the margin of error.
An estimate improves in accuracy in direct relation to the level of detail considered. A methodology defines the sequence of events by which parts are assembled. For example, a construction methodology identifies all of the resources of a product, such as lumber, steel, glass, etc. and how they are assembled. An Information Systems related methodology, such as&amp;nbsp;&amp;ldquo;PRIDE&amp;rdquo;-ISEM, specifies the sequence by which data elements, records, files, inputs, outputs, processes, etc. are assembled.&amp;nbsp;
This provides the ability to use a &amp;ldquo;bill of materials&amp;rdquo; (BOM) technique to count all of the resources in the product and develop an estimate for the project, in part or in full, based on the standards developed for completing and/or installing a resource. This is why &amp;ldquo;PRIDE&amp;rdquo; methodologies put an emphasis on &amp;ldquo;rough designs&amp;rdquo; in the early phases of work.
To better understand the BOM concept, consider all products are composed of a variety of parts, be it electronics, automobiles, airplanes, ships, bridges, skyscrapers, homes, etc. Using BOM, the various components are identified and related to the other parts they will be attached. To illustrate, here is a lawn mower showing all of the parts, identified by number and name, along with their relationships:

Such illustrations can typically be found in most product warranty guides. Obviously, BOM is an old concept used by engineers and architects for many years, but they can also be applied to information systems involving sub-systems (business processes), procedures (both administrative and computer), programs, files, inputs, outputs, records, and data elements. It can also be used in programming components, such as modules. To think of systems in this manner is somewhat of a revolutionary concept.

From such designs, the Project Manager is asked to consider:
* The number and types of NEW components to be created.
* The number and type of existing components requiring MODIFICATION.
* The number and type of existing components that can be RE-USED as is (no modification required).
To illustrate, in a &amp;ldquo;PRIDE&amp;rdquo;-ISEM Project (Phase 1), a complete &amp;ldquo;rough design&amp;rdquo; of the envisioned system is produced in Activity F. In Activity G, the Project Manager takes the rough design and makes the following type of assessment:

    
        
            COMPONENTS
            NEW
            MODIFY
            RE-USE
        
        
            SYSTEM
            1
            
            
        
        
            SUB-SYSTEMS
            14
            
            
        
        
            ADMIN PROC
            23
            
            
        
        
            COMP PROC
            13
            
            
        
        
            PROGRAMS
            28
            
            
        
        
            MODULES
            33
            10
            112
        
        
            INPUTS
            17
            
            5
        
        
            OUTPUTS
            37
            13
            
        
        
            FILES
            56
            5
            43
        
        
            RECORDS
            250
            50
            306
        
        
            DATA ELEMENTS
            60
            257
        
    

&amp;nbsp;
This analysis is essentially no different than other products consisting of different components, such as circuit boards, chips, nails, screws, lumber, girders, glass, gaskets, pistons, etc.
In systems, the rough design is used as the road map for the project (in the above example, there will have to be 14 Phases 3-7 because there are 14 sub-systems and 13 Phase 4-II &amp;amp; 6 for the 13 computer procedures, and at least 28 Phase 5&amp;rsquo;s for the programs). It is also the basis for the project estimate. Such estimating is greatly facilitated through the use of an IRM Repository which controls the components and, as such, acts like a Bill of Materials Processor (BOMP).
The BOM concept permits the establishment and application of estimating guidelines. To illustrate; how much direct time does it take to weld a six inch pipe? Define a data element? Design a sub-system? Such standards should be based on whole work (Direct Time) as opposed to including interferences (Indirect Time). Indirect time is a part of the work environment and can vary from company to company, group to group, even person to person. Estimating, therefore, must be accomplished using Direct hours only.
Having standards in place, we can then consider variations based on the skills of the worker. For example, how long it takes a novice worker to weld a product will certainly be longer than an expert. The same is true in systems analysis and programming. This is where a&amp;nbsp;Skills Inventorycomes in handy to select the appropriate worker for a project assignment.
By making system designers build a rough design of the product early in a project, the bill of materials can be populated accordingly and greatly improve estimating accuracy. As the project progresses, and changes are identified in the product structure, revisions in estimates can be easily made.
This is all made possible by using an engineering/manufacturing approach in the design and development of products, including systems.
Keep the Faith!
Note: All trademarks both marked and unmarked belong to their respective companies.
Author: Tim Bryce, Managing Directory, M&amp;amp;JB Investment Company
Tim Bryce is a writer and the Managing Director of&amp;nbsp;M&amp;amp;JB Investment Company&amp;nbsp;(M&amp;amp;JB) of Palm Harbor, Florida and has over 30 years of experience in the management consulting field. He can be reached attimb001@phmainstreet.com
Copyright&amp;nbsp;&amp;copy;&amp;nbsp;2015 by Tim Bryce. All rights reserved.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Sun, 29 Oct 2017 13:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3235</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1712/Is-the-Tail-Wagging-the-Dog.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1712</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1712&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Is the Tail Wagging the Dog?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1712/Is-the-Tail-Wagging-the-Dog.aspx</link> 
    <description>The point is, no amount of elegant programming can solve a system problem without someone who understands the overall system architecture, someone who understands how the business works. Attacking systems development without such orchestration, such as one program at a time, will not produce the desired results. That would be like trying to build a bridge without a set of blueprints; it would probably be disjointed and one end would likely not connect with the other in the middle.&amp;nbsp;</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 06 Jul 2017 10:25:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1712</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3740/The-State-of-IT-in-Business.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3740</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3740&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The State of I.T. in Business</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3740/The-State-of-IT-in-Business.aspx</link> 
    <description>Watching the speed by which Information Technology (I.T.) has changed over the last forty years has been amazing. Hardly a day goes by without some new twist or invention. In particular, my interest is in how I.T. can be applied to support the systems needed to operate a business, such as for manufacturing, inventory, order processing, customer service, accounting, human resources, and much more. I have seen a lot during the last four decades, perhaps too much.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 23 Mar 2017 18:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3740</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3511/Information-Driven-Design.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3511</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3511&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Information Driven Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3511/Information-Driven-Design.aspx</link> 
    <description>It appears to me people still have trouble defining information requirements and, as such, they are at a loss as to how to build total systems. Thereby, they are content building either a single business process or a program. Therefore, here is the conceptual foundation for all system design.  Information Driven Design begins with a simple concept...</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 20 Apr 2016 20:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3511</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3472/Nobody-Thinks-Big-Anymore.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3472</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3472&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Nobody Thinks Big Anymore</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3472/Nobody-Thinks-Big-Anymore.aspx</link> 
    <description>While others are moving forward introducing new banking products, the Americans find themselves in the role of constantly fighting fires. You cannot move forward until you put your house in order by bringing standard practices and discipline into your work effort. This is what happens when you treat system design as an art form, as opposed to a science.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 25 Feb 2016 10:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3472</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3375/The-Perils-of-Not-Knowing-Your-Responsibilities.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3375</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3375&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Perils of Not Knowing Your Responsibilities</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3375/The-Perils-of-Not-Knowing-Your-Responsibilities.aspx</link> 
    <description>In addition to the fundamental duties and responsibilities of an employee, it is not uncommon for workers to misunderstand their various project assignments. Consequently time and money is lost as employees try to delineate their responsibilities, including their relationship with co-workers.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 09 Dec 2015 11:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3375</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3389/Understanding-Business-Process-Design.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3389</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3389&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Understanding Business Process Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3389/Understanding-Business-Process-Design.aspx</link> 
    <description>There are several interpretations of Business Process Design, which is concerned with devising a cost-effective approach for the various tasks to be performed in a business. Here is mine which has worked effectively for me for several years. It&#39;s not a matter of what tools I use, but rather understanding the principles behind the design process itself.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 12 Nov 2015 05:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3389</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3354/Managing-Complexity.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3354</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3354&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Managing Complexity</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3354/Managing-Complexity.aspx</link> 
    <description>In a recent Information Technology discussion group I am involved with, someone posed the question,&amp;nbsp;&quot;What is complexity?&quot;&amp;nbsp;I was surprised by the question as I thought it was understood what complexity was all about. Evidently not. The person posing the question was primarily concerned with complexity in system design...</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 30 Sep 2015 20:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3354</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3300/The-Systems-Industry.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3300</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3300&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The &quot;Systems&quot; Industry</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3300/The-Systems-Industry.aspx</link> 
    <description>Whenever I mention I am in the &quot;Systems&quot; business, people generally look at me befuddled, smile, and shake their heads. I can tell they haven&#39;t got a clue what I am talking about. Many assume it has something to do with computers, and those in the technology sector assume I am referring to software. Frankly, no.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 03 Sep 2015 12:24:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3300</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3318/The-USDAs-System-Snafu.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3318</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3318&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The USDA&#39;s System Snafu</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3318/The-USDAs-System-Snafu.aspx</link> 
    <description>&amp;nbsp;They took a software approach for designing MIDAS as opposed to a system approach. For example, they probably created a data base quickly, then tried to figure how to get data in and out of it. I would suspect the program source code was well written, probably using &quot;Agile&quot; techniques, but the fact remains none of it was designed to work in a concerted manner.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 23 Jul 2015 11:16:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3318</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3258/Information-Resource-Myopia.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3258</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3258&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Information Resource Myopia</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3258/Information-Resource-Myopia.aspx</link> 
    <description>I have come to realize the practitioners in this industry suffer from acute myopia regarding their work. Programmers tend to believe their part of the puzzle is the most important, as do business process analysts, data base analysts, network analysts, project managers, enterprise analysts, etc.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 07 May 2015 11:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3258</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3238/Process-Templates.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3238</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3238&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Process Templates</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3238/Process-Templates.aspx</link> 
    <description>Based on requirements, ASE decomposes a system into its sub-systems (business processes), the procedural work flow for each, and determine what programs are necessary to implement the computer procedures (software specs). To do this, we determined there were three basic types of sub-systems...</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Mon, 20 Apr 2015 02:50:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3238</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3214/Methodology-Design-101.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3214</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3214&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Methodology Design 101</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3214/Methodology-Design-101.aspx</link> 
    <description>...the fact remains, you cannot build anything of substance, be it a system or otherwise, without a methodology. The question then becomes, how to construct a methodology suitable for your company or a given project. To this end, I offer this tutorial on designing methodologies.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Fri, 13 Mar 2015 10:54:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3214</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3169/Your-Duties-as-an-Employee.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3169</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3169&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Your Duties as an Employee</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3169/Your-Duties-as-an-Employee.aspx</link> 
    <description>In the corporate world, when we join a company, we are normally presented with several documents from the Human Resources department which we are asked to sign. As a newcomer, you would be wise not to rush through this process and review each document carefully. If you have questions, ask. You do not want to be surprised if a problem arises during your employment or afterwards as an ex-employee</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Fri, 06 Mar 2015 19:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3169</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3179/The-RIGHT-andWRONG-of-Design.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3179</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3179&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The &quot;RIGHT&quot; and&quot;WRONG&quot; of Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3179/The-RIGHT-andWRONG-of-Design.aspx</link> 
    <description>People ask me why I seem to be &amp;ldquo;black and white&amp;rdquo; on so many issues. Two reasons come to mind: first, I learned early in school that you do not get credit for making a mistake. If this has changed, please let me know. Second, the nature of my work in the information systems world has taught me there are right ways of doing things, as well as wrong ways. I am also not embarrassed to admit, &amp;ldquo;I do not know,&amp;rdquo; when I am unsure of myself, and will endeavor to find the answer. Failure to admit this is a sign of weakness, as is fabricating an excuse or leading someone down the wrong path.

In the many industries I have consulted with, I have learned there are right ways and wrong ways for conducting business:

* In manufacturing, there are defined methodologies for assembling just about any type of product, be it electronics, automobiles, ships, jet engines, or jets themselves. If the manufacturing sequence is not performed correctly, quality will suffer and defects will likely ensue.

* In the restaurant business, there are defined methodologies for cooking and customer service. If the cook mixes up the sequence of the recipe, believe me, you won&amp;rsquo;t want to eat it.

* The construction industry is no different. Regardless of what you are building, there is a defined sequence of tasks. As a hint, when you are building a house, it is generally a good idea to lay the foundation before you start constructing the roof.

* In information systems, you better have a clear understanding of the information requirements before designing the business processes, data base, work flows, and software. Unfortunately, most systems projects are doomed from the outset as they skip over requirements and begin to program almost immediately.

The lesson here is simple; if you perform the wrong task at the wrong time in a methodology, you are doomed. As any craftsman can tell you, it is not so much about the tools you use as it is about the methodology. Skipping steps represents a calculated risk to the success of a project. Believe it or not, people in the systems field fail to comprehend this simple concept. They are convinced specifying requirements and performing the steps for design is a colossal waste of time, with the the real work being in programming. This is like suggesting we build a bridge without first studying the problem and laying out the architectural plans; that the builders should show up at the job site and begin hammering and cutting the pieces of the bridge together without a set of blueprints. Let&amp;rsquo;s face it, if we built bridges in the same manner as we build systems in this country, this would be a nation run by ferryboats.

There is a science to building just about anything, be it a skyscraper, a bridge, an automobile, or an information system. It is all based on proven principles of design, it is hardly an artistic endeavor. This is not to suggest design is void of creativity; hardly, but a science is teachable and does not rely on a person&amp;rsquo;s intuition. Basically, it requires discipline which is something sorely lacking in the IT industry where people prefer &amp;ldquo;shooting from the hip&amp;rdquo; as opposed to learning the proper mechanics of a methodology.

As an aside, I have a friend in the art world who teaches illustration at a Midwest College. He too appreciates the need for methodology. As he adamantly instructs his students, it is not simply about starting to draw an illustration using paper and pencil, but the necessary steps for producing a proper graphic. So you see, even in the artwork there are &amp;ldquo;right&amp;rdquo; ways and &amp;ldquo;wrong&amp;rdquo; ways for doing something. It&amp;rsquo;s called a &amp;ldquo;methodology.&amp;rdquo;

Yes, it really is that &amp;ldquo;black and white.&amp;rdquo; Next question?

Keep the Faith!

Note: All trademarks both marked and unmarked belong to their respective companies.

Author: Tim Bryce is a writer and the Managing Director of M&amp;amp;JB Investment Company (M&amp;amp;JB) of Palm Harbor, Florida and has over 30 years of experience in the management consulting field. He can be reached at timb001@phmainstreet.com

For Tim&amp;rsquo;s columns, see:  timbryce.com

Copyright &amp;copy; 2015 by Tim Bryce. All rights reserved.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 29 Jan 2015 10:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3179</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3063/A-Job-Description-for-Business-Analysis.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3063</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3063&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>A Job Description for Business Analysis</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3063/A-Job-Description-for-Business-Analysis.aspx</link> 
    <description>Makes me wonder if the industry really grasps the duties and responsibilities of the BA. The industry talks about such people, but have we standardized a job description? We wrote several such descriptions as part of our &amp;ldquo;PRIDE&amp;rdquo; Methodologies for IRM and based on this, let me see if I can establish a standard job description.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 28 Aug 2014 13:16:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3063</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3007/Who-is-Designing-Your-Systems.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3007</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3007&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Who is Designing Your Systems?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3007/Who-is-Designing-Your-Systems.aspx</link> 
    <description>Problems arise though when the critical front-end work is performed by programmers who are more in tune with technology than business. From their perspective, they see everything in terms of zeroes and ones, not in dollars and cents. Not surprising, they only think in terms of elegant technical solutions, not necessarily what is practical from a business perspective.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 16 Jul 2014 10:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3007</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2990/Logical-Systems.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2990</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2990&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Logical Systems</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2990/Logical-Systems.aspx</link> 
    <description>I have had business friends over the years ask me why it seems so difficult and time consuming to upgrade their corporate systems to take advantage of the latest computer technology. In their minds, their systems are relatively simple; the concepts of such things as accounts receivable, accounts payable, inventory, manufacturing, etc. are relatively straight forward. Yet, companies incur millions of dollars in keeping them up-to-date. The question is, &quot;Why?&quot;</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 19 Jun 2014 06:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2990</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2985/Creating-Universal-Systems.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2985</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2985&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Creating Universal Systems</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2985/Creating-Universal-Systems.aspx</link> 
    <description>In this day and age of &amp;ldquo;globalization&amp;rdquo; more and more Information Systems are crossing geographical boundaries. Because of this, serious consideration should be given to making systems universally applicable to any country. Some might consider this an impossible task, but it is actually easier than you might think. It just requires a little common sense and some planning.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 11 Jun 2014 02:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2985</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2969/Pre-or-Post-Documentation-Which-do-you-Prefer.aspx#Comments</comments> 
    <slash:comments>4</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2969</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2969&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Pre or Post Documentation, Which do you Prefer?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2969/Pre-or-Post-Documentation-Which-do-you-Prefer.aspx</link> 
    <description>Some programmers consider documentation a waste of time (see “Agile  programming”), even going so far as to claim it is detrimental to  productivity. Instead of getting all the software specifications  recorded on paper at the start, they prefer to begin hacking on the  program code and keep modifying it until the end-user is satisfied.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 22 May 2014 00:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2969</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2853/Hi-Ho-Hi-Ho-Its-Back-To-Work-We-Go.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2853</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2853&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Hi Ho, Hi Ho, It&#39;s Back To Work We Go</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2853/Hi-Ho-Hi-Ho-Its-Back-To-Work-We-Go.aspx</link> 
    <description>It&#39;s a new year, and time to go back to work. January is when we reset the statistics, brace for a new year, and try to prove ourselves once again.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 22 Jan 2014 05:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2853</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2767/Its-All-About-Transactions.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2767</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2767&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>It&#39;s All About Transactions</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2767/Its-All-About-Transactions.aspx</link> 
    <description>It is important to illustrate most of what goes on in the systems and software world is really not as complicated as people make it.&amp;#160; Most of what we do in business is process transactions, representing some sort of action or event, such as a purchase, a return, a back-order, a debit or a credit.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 30 Oct 2013 07:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2767</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2693/Five-Easy-Lessons-for-System-Design.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2693</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2693&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Five Easy Lessons for System Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2693/Five-Easy-Lessons-for-System-Design.aspx</link> 
    <description>I never really understood the hubbub associated with system design. People tend to look upon it as a complicated process. Actually it&#39;s not, yet the corporate landscape is littered with disastrous system projects costing millions of dollars, all because developers overlooked some rather simple principles for design and focused on technology instead.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 07 Aug 2013 06:39:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2693</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2569/Understanding-the-Natural-System.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2569</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2569&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Understanding the Natural System</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2569/Understanding-the-Natural-System.aspx</link> 
    <description>Every now and then I encounter a programmer who adamantly contends you cannot have an information system without some form of computer support. Actually, we&#39;ve had such systems well before the advent of the computer.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 25 Apr 2013 06:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2569</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2549/How-Information-Affects-Micromanagement.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2549</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2549&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How Information Affects Micromanagement</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2549/How-Information-Affects-Micromanagement.aspx</link> 
    <description>Managers should do some soul-searching; do they really need that information or are they interfering with the responsibilities of others? My advice to managers is simple: Delegate responsibility, hold people accountable, and get out of their way.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Mon, 01 Apr 2013 08:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2549</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2399/The-Language-of-Systems.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2399</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2399&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Language of Systems</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2399/The-Language-of-Systems.aspx</link> 
    <description>The language of systems is no different; No, it is not C++, Java, COBOL, etc., but rather simple English (or whatever your native language happens to be). In the past I have gone into length about the differences between Systems and Software, the two are simply not synonymous. Whereas systems include business processes implemented by human beings, computers and other office equipment, software is simply instructions for the computer to follow. Systems are for people who must also take an active role in its execution. In fact, systems will fail more for the lack of people procedures than they will for well-written computer software.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 08 Nov 2012 10:11:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2399</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2134/Methodologies-The-Dance-of-the-Fairies.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2134</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2134&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Methodologies &amp; The Dance of the Fairies</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2134/Methodologies-The-Dance-of-the-Fairies.aspx</link> 
    <description>In a nutshell, a methodology represents a series of steps in a project specifying Who is to perform What, When, Where, Why, and How (aka, &quot;5W+H&quot;), from start to finish. Perhaps the best way to think of a methodology is as a roadmap or an assembly line where a product is developed over a series of work stations.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 26 Jan 2012 08:19:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2134</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1928/Estimating--Getting-it-Right.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1928</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1928&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Estimating - Getting it Right</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1928/Estimating--Getting-it-Right.aspx</link> 
    <description>It seems every now and then someone comes along with a new spin on how to estimate a project, either in its entirety or a portion of it. I have heard a lot of theories over the years, particularly in the Information Technology (I.T.) field where there is a tendency to pull numbers out of a hat, but I&#39;ve long given up looking for panaceas.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 28 Jul 2011 02:36:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1928</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1907/The-DoctorPatient-Analogy-for-Problem-Definition.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1907</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1907&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Doctor/Patient Analogy for Problem Definition</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1907/The-DoctorPatient-Analogy-for-Problem-Definition.aspx</link> 
    <description>Over the years I have noticed that we, as Americans, seem to possess a knack for attacking the wrong problems which I refer to as the “Rearranging the deck chairs on the Titanic” phenomenon. I see this not only in the corporate world, but in our private lives as well. Instead of addressing the correct problems, we tend to attack symptoms.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Tue, 05 Jul 2011 06:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1907</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1891/Another-Mega-System-Disaster.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1891</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1891&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Another Mega-System Disaster</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1891/Another-Mega-System-Disaster.aspx</link> 
    <description>Recently, I was watching an episode of &quot;60 Minutes&quot; which discussed the prosecution of a whistle blower at the NSA regarding the development of a major system to be used in the War on Terror, code named &quot;Trailblazer.&quot;&amp;#160;Although the intentions of the developers may have been good, the project started to spiral out of control almost from the beginning.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 30 Jun 2011 09:02:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1891</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1622/Enterprise-Engineering.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1622</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1622&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Enterprise Engineering</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1622/Enterprise-Engineering.aspx</link> 
    <description>&quot;Enterprise Engineering&quot; is a term coined in&amp;#160;to reflect the third and final part of&amp;#160;the concept of Information Resource Management (IRM) representing a triad of methodologies to design, develop, and control all of the resources needed to support the information requirements of an enterprise, be it a commercial or nonprofit endeavor.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Fri, 19 Nov 2010 18:43:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1622</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1552/Three-Types-of-Design-Effort.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1552</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1552&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Three Types of Design Effort</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1552/Three-Types-of-Design-Effort.aspx</link> 
    <description>In I.T., are we really spending too much time on &quot;maintenance&quot;?&amp;#160; Within any systems development organization, there are but three types of work effort: new systems development, maintenance, and modification/improvements. A mature development organization will spend approximately 5% of its time on new development, 10% on maintenance, and 85% of its time on modification/improvements.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Sat, 18 Sep 2010 16:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1552</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1494/True-Systems-Analysis.aspx#Comments</comments> 
    <slash:comments>16</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1494</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1494&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>True Systems Analysis?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1494/True-Systems-Analysis.aspx</link> 
    <description>Regretably, many of today&#39;s Systems Analysts are still glorified programmers in sheep&#39;s clothing.&amp;#160; I recently came across some job postings under the title, &quot;Systems Analyst,&quot; and it occurred to me people still do not know what it means. In the postings I saw things like&amp;#160;&quot;seeking a Systems Analyst with 4 - 6 years experience...&amp;#160;Candidate must have experience with JAVA and the ATG application framework.&quot;
&amp;#160;</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Fri, 03 Sep 2010 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1494</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1085/The-Problem-with-Man-Hours.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1085</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1085&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Problem with &quot;Man Hours&quot;</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1085/The-Problem-with-Man-Hours.aspx</link> 
    <description>I&#39;ve never been comfortable with the concept of &quot;Man Hours,&quot; not that it&#39;s a gender issue, but rather it implies ignorance of how time is used in the work place and fumbles away some simple management concepts needed to run any business, namely accountability and commitment. Actually, I thought the &quot;Man Hour&quot; concept disappeared with the passing of the 20th century, but it appears to be making a comeback.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Fri, 25 Sep 2009 04:53:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1085</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1056/Information-Systems-Theory-101.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1056</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1056&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Information Systems Theory 101</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1056/Information-Systems-Theory-101.aspx</link> 
    <description>Systems work is not as hard as you might think. However, we have a tendency in this business to complicate things by changing the vocabulary of systems work and introducing convoluted concepts and techniques, all of which makes it difficult to produce systems in a consistent manner. Consequently, there is a tendency to reinvent the wheel with each systems development project. I believe I owe it to my predecessors and the industry overall to describe basic systems theory, so that people can find the common ground needed to communicate and work. Fortunately, there are only four easy, yet important, concepts to grasp which I will try to define as succinctly as possible.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 20 Aug 2009 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1056</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/474/Understanding-Group-Data-Elements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=474</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=474&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Understanding Group Data Elements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/474/Understanding-Group-Data-Elements.aspx</link> 
    <description>In the past I have discussed the need to manage data (and all information resources) as a valuable resource; something to be shared and reused in order to eliminate redundancy and promote system integration.&amp;nbsp; Now, our attention turns to how data should be defined.&amp;nbsp; Well defined data elements are needed in order to properly design the logical data base as well as developing a suitable physical implementation.
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Tue, 01 Jul 2008 14:13:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:474</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/458/Current-Systems-Analysis.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=458</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=458&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Current Systems Analysis</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/458/Current-Systems-Analysis.aspx</link> 
    <description>The subject of current systems analysis is usually greeted with dismay or disdain by systems departments. There are many reasons for this. In many installations, the support of current systems takes more than 85% of the systems department&amp;#39;s time, and the departments are more than ready to get on with new systems development and bury the old, non-working systems as quickly as possible. In cases where systems do not require a lot of maintenance, the systems department may find that the current systems are not giving management the kind of information it needs for effective decision making; these current systems become likely candidates for replacement.

However, there are some very legitimate reasons for documenting existing systems...
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 18 Jun 2008 11:41:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:458</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/441/System-Design-Backwards.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=441</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=441&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>System Design Backwards</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/441/System-Design-Backwards.aspx</link> 
    <description>One of the biggest challenges in any system design effort is to produce a viable system design that is well thought-out with all of the pieces and parts working harmoniously together. If something is forgotten, regardless of its seeming insignificance, it will undoubtedly cause costly problems later on. The task, therefore, is to produce a design that is demonstratively correct.
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 04 Jun 2008 16:23:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:441</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/375/Stepwise-Refinement.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=375</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=375&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Stepwise Refinement</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/375/Stepwise-Refinement.aspx</link> 
    <description>In a nutshell, the concept of &amp;quot;stepwise refinement&amp;quot; is to take an object and move it from a general perspective to a precise level of detail. Architects have used such an approach for years, as have engineers building products. But to do so, they realized they cannot simply go from the general to the specific in one felled swoop, but instead, in increments (steps). The number of steps needed to decompose an object into sufficient detail is ultimately based on the inherent nature of the object. To illustrate, for architects designing a building, the typical steps include:


 Develop artist rendering (to consider viability).
 Design foundation and superstructure.
 Design Floor plans.
 Design electrical and plumbing diagrams.


Author: Tim Bryce
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Fri, 30 May 2008 11:48:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:375</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/355/Why-We-Resist-Planning.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=355</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=355&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Why We Resist Planning</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/355/Why-We-Resist-Planning.aspx</link> 
    <description>The short answer: &amp;quot;Because it requires work.&amp;quot;

The long answer: People tend to resist gazing into the crystal ball and prefer to react to life as it passes them by. Some people believe planning&amp;nbsp;in today&amp;#39;s ever changing world is a waste of time, that you must be more &amp;quot;agile&amp;quot; and accommodate changes as they occur. As anyone who has designed and built anything of substance knows, this is utterly ridiculous. We would not have the many great skyscrapers, bridges, dams, highways, ships, planes, and other sophisticated equipment without the efforts of architects and engineers. Without such planning, our country would look essentially no different than how the pioneers first discovered the continent. Although we must certainly be flexible in our plans, and we will inevitably make some mistakes along the way, little progress would be made if we did not try to plan a course of action and control our destiny.

People often take planning for granted, that someone else will be making plans for us, such as government officials, our corporate management, or even the elders of our families. Consequently we become rather lax about looking into the future. Nor is there any encouragement by anyone to plan our affairs, such as a tax break. Whereas other countries offer incentives to save money for the future, such as Japan, America does not. Therefore, planning is a rather personal activity; we either see the virtue in doing so or we do not.

Author: Tim Bryce
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 07 May 2008 14:47:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:355</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/348/Why-IT-Standards-Fail.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=348</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=348&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Why IT Standards Fail</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/348/Why-IT-Standards-Fail.aspx</link> 
    <description>Standardization offers the benefits of uniformity, predictability, interchangeability, and harmony. If this is not of interest to you, than there is little point in trying to participate in a standards program. But if you do wish to participate, understand there is more to implementing standards than to just say &amp;quot;that&amp;#39;s just how it is going to be done.&amp;quot; There has to be some sound rationale for their governance. In addition, you must address the enforcement issue. Standards will be adhered to by the degree of discipline instilled in the staff; If well disciplined, your chances for success are good, but if discipline is lax, automation is required to assure standards are being followed.
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 30 Apr 2008 10:31:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:348</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/338/Is-PRIDE-too-rigid.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=338</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=338&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Is PRIDE too rigid?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/338/Is-PRIDE-too-rigid.aspx</link> 
    <description>I was recently asked by an &quot;Agile&quot; proponent if I thought our &quot;PRIDE&quot; methodologies were too rigid for today&#39;s fast-paced Information Technology world, that perhaps it was too bureaucratic. First, I pointed out that &quot;PRIDE&quot; was more of a way of thinking as opposed to anything else. You can remove all of the documentation associated with the methodologies, including the forms, and still produce a system for example. This took him aback somewhat as he had thought of &quot;PRIDE&quot; as an inflexible paper mill...
Discusses the implementation of a robust Systems Design Methodology.
Author: Tim Bryce</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 16 Apr 2008 11:42:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:338</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/332/Covering-for-Incompetence.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=332</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=332&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Covering for Incompetence</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/332/Covering-for-Incompetence.aspx</link> 
    <description>The pointy haired manager in Scott Adams&amp;#39; &amp;quot;Dilbert&amp;quot; cartoon has become an icon for management incompetence. Although Adams&amp;#39; character may seem like an extreme, we have all encountered various examples of the Peter Principle whereby people have risen above their level of competency. We see this not only in our companies, but also in the nonprofit organizations we are involved in. Basically, these are some very nice people who simply haven&amp;#39;t a clue as to what they are doing and stumble through each day making bad decisions which drives their subordinates to madness.

Author: Tim Bryce
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 10 Apr 2008 19:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:332</guid> 
    
</item>

    </channel>
</rss>